Task: Define Intake Of The Test Object (AST)
Purpose
To establish whether the delivered parts of the test object function in such a way that adequate testing can be carried out.
Relationships
RolesPrimary Performer: Additional Performers:
Outputs
    Process Usage
    Main Description

    Method of operation

    The method of operation includes the following steps:

    1. Checking completeness of the delivered test object
    2. Executing the pre-test.

    A condition of the execution of these subactivities is that the required test infrastructure is available. This means effectively that the intake of the infrastructure should have gone successfully. A successful pre-test is a condition for the starting of the subsequent activities in the Execution phase. The defects from the pre-test are registered and, if a defect is test-obstructive, it is immediately submitted to the parties involved. Every effort should be made, with the highest priority, to solve the test-obstructive defects and allow the pre-test to complete successfully (see Carry Out Intake Of The Infrastructure (AST)).

    Products
    • Defects
    • Installed and testable test object.

    Tools

    • Testware management tool
    • Defect management tool
    • Automated test execution tool
    • Monitoring tool
    • Comparator
    • Database manipulation tool
    • Simulator
    • Stubs and drivers

    Steps
    1. Checking completeness of the delivered test object
    With the aid of the checklist created in the Specification phase, the delivered test object is checked for completeness. This is done by the test manager, assisted by (where this role is taken) the test infrastructure coordinator. Missing parts are reported, by means of a defect, to the parties involved. If the defect is test-obstructive (i.e. the subsequent subactivity, the pre-test, cannot start), then this should be solved immediately. It is advisable to carry out this subactivity together with the department that maintains the test environment, since this department depends on a complete delivery of the test object, otherwise the installation will be wrong. Moreover, they have the technical knowledge to be able to check the test object on the aspect of completeness. Following approval, the test infrastructure coordinator can install the test object (or have the administrators do so).
    2. Executing the pre-test

    As soon as a (version of the) test object is installed, it is important to carry out a pre-test. This takes place before the actual testing begins. The purpose of the pre-test is to evaluate whether the test object is of sufficient quality for testing. The pre-test is carried out by executing the test script that was created for this during the Specification phase. It regularly happens in practice that systems are wrongly delivered or wrongly installed in the first days of testing, thus delaying the start of the test execution. This is not only a waste of time, it also demotivates the test team. It is important to consider this when creating the test plan (see also Determine The Planning (AST)).


    More Information
    Guidelines
    Tool Mentors

    Copyright © 2006, Sogeti Nederland B.V. All rights reserved.